home *** CD-ROM | disk | FTP | other *** search
/ NetNews Offline 2 / NetNews Offline Volume 2.iso / news / comp / std / c++ / 288 < prev    next >
Encoding:
Internet Message Format  |  1996-08-06  |  1.9 KB
  1. From: clamage@eng.sun.com (Steve Clamage)
  2. Message-ID: <4f69po$9lu@engnews1.Eng.Sun.COM>
  3. X-Original-Date: 6 Feb 1996 01:10:16 GMT
  4. Path: in2.uu.net!bounce-back
  5. Date: 06 Feb 96 02:43:30 GMT
  6. Approved: fjh@cs.mu.oz.au
  7. Newsgroups: comp.std.c++
  8. Subject: Re: and, or, not
  9. Organization: Sun Microsystems Inc.
  10. References: <DMBG7p.H7z@infosoft.com>
  11. Reply-To: clamage@eng.sun.com
  12. X-Auth: PGPMoose V1.1 PGP comp.std.c++
  13.     iQBFAgUBMRbAi+EDnX0m9pzZAQEBfQF/cDpfZ+GgXKWqc0XL51+1vo40EGAtZyT1
  14.     kHOe1ajf85XcHU4to/G0U6tBU6YDv8t/
  15.     =1+/4
  16.  
  17. In article H7z@infosoft.com, jgalt@infosoft.com (John Galt) writes:
  18. >In article <1198@dawes.win.net>, Beman Dawes <beman@dawes.win.net> wrote:
  19.  
  20. >>  2.9  Keywords                                                [lex.key]
  21.  
  22. >[snip]
  23.  
  24. >>                   Table 4--alternative representations
  25. >
  26. >>            +------------------------------------------------+
  27. >>            |and      and_eq   bitand   bitor   compl    not |
  28. >>            |not_eq   or       or_eq    xor     xor_eq       |
  29. >>            +------------------------------------------------+
  30.  
  31. >This leads to another question:
  32.  
  33. >Assuming that the problem characters (those that don't exist on some
  34. >keyboards, making the above names necessary) are &, |, !, ^, and ~, I
  35. >wonder why they didn't create names for all the affected characters. 
  36. >I would have done something like this: ...
  37.  
  38. As I said in an earlier article, the C++ Committee didn't invent the
  39. alternative representations, and didn't even particularly like some
  40. of them. They were previously adopted as part of another ISO standard.
  41. It seemed much better to comply with an existing standard than to
  42. create an incompatibility.
  43.  
  44. ---
  45. Steve Clamage, stephen.clamage@eng.sun.com
  46. ---
  47. [ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  48.   Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  49.   is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
  50.